Do not use the standard system startup files when link-
ing. The standard libraries are used normally.
----nnnnoooossssttttddddlllliiiibbbb
Don't use the standard system libraries and startup
files when linking. Only the files you specify will be
passed to the linker.
----ssssttttaaaattttiiiicccc
On systems that support dynamic linking, this prevents
linking with the shared libraries. On other systems,
this option has no effect.
----sssshhhhaaaarrrreeeedddd
Produce a shared object which can then be linked with
other objects to form an executable. Only a few sys-
tems support this option.
----ssssyyyymmmmbbbboooolllliiiicccc
Bind references to global symbols when building a
shared object. Warn about any unresolved references
(unless overridden by the link editor option `----XXXXlllliiiinnnnkkkkeeeerrrr
----zzzz ----XXXXlllliiiinnnnkkkkeeeerrrr ddddeeeeffffssss'). Only a few systems support this
option.
----XXXXlllliiiinnnnkkkkeeeerrrr _o_p_t_i_o_n
Pass _o_p_t_i_o_n as an option to the linker. You can use
this to supply system-specific linker options which GNU
CC does not know how to recognize.
If you want to pass an option that takes an argument,
you must use `----XXXXlllliiiinnnnkkkkeeeerrrr' twice, once for the option and
once for the argument. For example, to pass `----aaaasssssssseeeerrrrtttt
ddddeeeeffffiiiinnnniiiittttiiiioooonnnnssss', you must write `----XXXXlllliiiinnnnkkkkeeeerrrr ----aaaasssssssseeeerrrrtttt ----XXXXlllliiiinnnnkkkkeeeerrrr
ddddeeeeffffiiiinnnniiiittttiiiioooonnnnssss'. It does not work to write `----XXXXlllliiiinnnnkkkkeeeerrrr
""""----aaaasssssssseeeerrrrtttt ddddeeeeffffiiiinnnniiiittttiiiioooonnnnssss""""', because this passes the entire
string as a single argument, which is not what the
linker expects.
----WWWWllll,,,,_o_p_t_i_o_n
Pass _o_p_t_i_o_n as an option to the linker. If _o_p_t_i_o_n con-
tains commas, it is split into multiple options at the
commas.
----uuuu _s_y_m_b_o_l
Pretend the symbol _s_y_m_b_o_l is undefined, to force link-
ing of library modules to define it. You can use `----uuuu'
multiple times with different symbols to force loading
Return some structures of more than one word in regis-
ters, when convenient. This is the default. For com-
patibility with the IBM-supplied compilers, use either
`----ffffppppcccccccc----ssssttttrrrruuuucccctttt----rrrreeeettttuuuurrrrnnnn' or `----mmmmhhhhcccc----ssssttttrrrruuuucccctttt----rrrreeeettttuuuurrrrnnnn'.
These `----mmmm' options are defined for the MIPS family of com-
puters:
----mmmmccccppppuuuu====_c_p_u-_t_y_p_e
Assume the defaults for the machine type _c_p_u-_t_y_p_e when
scheduling instructions. The default _c_p_u-_t_y_p_e is ddddeeee----
ffffaaaauuuulllltttt, which picks the longest cycles times for any of
the machines, in order that the code run at reasonable
(C++ only.) Use this pragma in a main input file, when
you want full output from included header files to be
generated (and made globally visible). The included
header file, in turn, should use `####pppprrrraaaaggggmmmmaaaa iiiinnnntttteeeerrrrffffaaaacccceeee'.
Backup copies of inline member functions, debugging in-
formation, and the internal tables used to implement
virtual functions are all generated in implementation
files.
If you use `####pppprrrraaaaggggmmmmaaaa iiiimmmmpppplllleeeemmmmeeeennnnttttaaaattttiiiioooonnnn' with no argument,
it applies to an include file with the same basename as
your source file; for example, in `aaaallllllllccccllllaaaassssssss....cccccccc',
`####pppprrrraaaaggggmmmmaaaa iiiimmmmpppplllleeeemmmmeeeennnnttttaaaattttiiiioooonnnn' by itself is equivalent to
`####pppprrrraaaaggggmmmmaaaa iiiimmmmpppplllleeeemmmmeeeennnnttttaaaattttiiiioooonnnn """"aaaallllllllccccllllaaaassssssss....hhhh""""'. Use the string
argument if you want a single implementation file to
